Schema Extension Modification Registry view

Administration System Schema Extension Modification Registry Schema Extension Modification Registry view

The Schema Extension Modification Registry view lists:

• Customized system entities: Any Navis-delivered entity available at build time that has been customized with new dynamic flex fields. System entities are available in every build.

• Dynamic custom entities: Any customer-defined entity dynamically created at run time. You can add dynamic entity fields to these entities. Dynamic custom entities are only available in a specific build.

You use the Schema Extension Modification Registry view as a sandbox to:

• Add new fields to system entities (on page 1)

• Create or edit dynamic custom entities (on page 1)

You can only modify N4 entities, not XPS entities.

In addition, you can use the Actions menu to:

• Create Schema Snapshot (on page 1): Lock the schema extension modifications and create a snapshot of the database schema. Creating the snapshot may take a few minutes. When done, N4 opens both the Schema Extension Snapshot Registry (on page 1) view and the Model Extension Snapshot form (on page 1).

• View All Field History (on page 1): Open a consolidated view of all custom fields added to system and custom entities.

• Generate Schema Upgrade DLL for Current Definition: Generate the DLL to be executed if it were to be applied as a snapshot. The DLL includes all enabled modification entities. This option serves diagnostic purposes only.

N4 also automatically generates the DDL for review when you create a snapshot.

If you run into problems and are familiar with Hibernate, a 3rd party object-relational mapping library, you can right-click an entity and select Generate Debug HBM mapping. A hibernate mapping file includes the DDL to generate the database itself, Java classes to represent the entities, constants used to refer to entities and their fields in the code, and metafield definitions used to validate user input.

The changes you make in this view do not directly affect the schema. For this to happen, you need to:

1. Lock the current entries for a snapshot (Actions Create Schema Snapshot).

2. Approve the snapshot to be applied at restart (Schema Extension Snapshot Registry view Actions Reload Session Factory).

You can also edit and delete entities in this view. If you have not yet applied the entity to the database, deleting an entity in this view cleanly deletes the entity from the database, pending foreign key relations. However, if you have already applied the entity to the database, deleting the entity in this view only removes the entity from the application mode but not from the database. In this case, you must manually delete any custom tables from the database. In addition, if the deleted entity customized other components, you also need to delete or disable those components.

For information on the N4 domain model, see the documentation provided under Help Model Docs.

In some N4 versions, the link to this resource is not working. As a workaround, you can access the Model Docs directly from the N4 footprint installed on your server. From within the N4 application footprint, manually open the domainIndex.html file that is located at the following location (you should only see one of the following directory paths, not both):
Navis/sparcsn4/webapps/apex/model
Navis/sparcsn4/webapps/apex/argo

Schema Extension Modification Registry Columns